The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations
- Downloads：4871
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-11-17 10:21:30
- Update Date：2025-09-06
- Status：finish
- Author：Gene Kim
- ISBN：B09G2GS39R
- Environment：PC/Android/iPhone/iPad/Kindle
Reviews
James
，
Some really good case studies and ideas in a nice digestible format
Chris Hendriks
，
A quote from the book “the use of version control by Ops was the highest predictor of both IT performance and organizational performance。 In fact， whether Ops used version control was a higher predictor for both IT performance and organizational performance than whether Dev used version control。” says enough … read it at least twice！
Monica
，
Great book for anyone interested in DevOps practices and how they are implemented over many case studies。
Aaron
，
This is a reasonable， if surface-level， overview of the common best practice devops approaches these days -- continuous integration/delivery/deployment， agile approaches， full-stack developers， etc。It actually does a decent job as an overview， though I think the authors try to hit too much without really going into the intricacies of the fact that many of these concepts inherently conflict against each other （for example， microservices that can be managed by a single team and company-wide librar This is a reasonable， if surface-level， overview of the common best practice devops approaches these days -- continuous integration/delivery/deployment， agile approaches， full-stack developers， etc。It actually does a decent job as an overview， though I think the authors try to hit too much without really going into the intricacies of the fact that many of these concepts inherently conflict against each other （for example， microservices that can be managed by a single team and company-wide libraries cause problems as changes that are needed for a single service have cascading requirements down the chain of dependencies）， and the fact that the negatives are generally ignored makes me wonder a bit if this is more of a research paper and less of a real-world experience sort of deal。Regardless。。。 there's a few things that make me give this 3 stars。 Most importantly， there was literally zero new that I learned。 All of these practices I'm currently utilizing in work now， or have used in the past and opted not to for some reason currently。 I honestly feel bad for any developer or devops engineer that _doesn't_ already know all of this。。。 I imagine it's useful for someone working for a company that doesn't really get software， but have doubts that most of these ideas are going to go anywhere in that kind of company。 I suppose I'm not young or old enough for any of it to be news。Additionally， the authors take their interviews at their word， and at least in my experience， none of these devops approaches are quite as one-sided as they make it sound。 It adds to the sense that this is more like a biased argument than a more nuanced discussion of what works and what doesn't， and what the tradeoffs are。 If you didn't know there were tradeoffs， you'd be out of luck because they're barely discussed here at all。Lastly， tooling like CDK and infrastructure-as-code were totally missed， despite them being totally vital to ops， arguably even more than for developers。Would recommend for totally new devops， or those stuck working for a company that isn't technically adept。 If you're not checking in code every day-ish， that's probably you。 。。。more
Sarah
，
I had to read this book for work。 That's it; that's the review。 I had to read this book for work。 That's it; that's the review。 。。。more
Joel Hess
，
Good general tips and ideas。 Not a lot of depth， or detail that you couldn't find from googling。 We Book Clubbed it in our organization and it was good for guiding conversations。 Good general tips and ideas。 Not a lot of depth， or detail that you couldn't find from googling。 We Book Clubbed it in our organization and it was good for guiding conversations。 。。。more
Suphan Fayong
，
This book is about how modern software development should be handled。 Specifically the authors propose 3 big ideas:1） Improve speed and safety from development to deployment2） Improve speed and availability of feedback from production3） Improve learning and propagate it throughout the organizationThe main themes I notice in practices introduced in this books are:- Make as much automation as possible， specifically testing and deployment。- Make all important work as everyday job。 Deployment as eve This book is about how modern software development should be handled。 Specifically the authors propose 3 big ideas:1） Improve speed and safety from development to deployment2） Improve speed and availability of feedback from production3） Improve learning and propagate it throughout the organizationThe main themes I notice in practices introduced in this books are:- Make as much automation as possible， specifically testing and deployment。- Make all important work as everyday job。 Deployment as everyday job。 Writing tests as everyday job。 Putting telemetry in code as every job。 Security concerns as everyday job。 Anything treated as a separate part will be of low quality and resulting in long lead time e。g。 testing at the end of a project。One big downside （maybe not for some people） of this book is that the text is written in a story-telling fashion。 It contains a lot of stories that explain how good these practices are。 I read this book to primarily study the practices。 The benefits of the practices are secondary because I already know them （that's why I read this book in the first place）。 。。。more
David Mendoza
，
It’s a good starting for those who are not familiar with the DevOps culture。 The book introduces many helpful concepts and ideas to soften the relationship between different areas in IT and how they can converge in the daily work to start a continuous improvement cycle。 It’d be great if the book went deeper in some topics， however it helps to change the mindset。
Josh
，
My review will focus on the practical knowledge gained through reading this， which at its core seems like a useful （if not exhaustive） reference for anyone adjacent to DevOps practices and who wants to learn more。 The reviews from 'seasoned DevOps and Continuous Delivery practitioners' complaining about the content are downright strange， since they are quite clearly not the intended audience: aside from the directive in the introduction to 'create a working knowledge。。' to 'serve as a primer' fo My review will focus on the practical knowledge gained through reading this， which at its core seems like a useful （if not exhaustive） reference for anyone adjacent to DevOps practices and who wants to learn more。 The reviews from 'seasoned DevOps and Continuous Delivery practitioners' complaining about the content are downright strange， since they are quite clearly not the intended audience: aside from the directive in the introduction to 'create a working knowledge。。' to 'serve as a primer' for business leaders/stakeholders as well as readers who are not wholly familiar with DevOps practices， it ought to be clear from the title （a "Handbook"！） that this is not intended as an advanced analysis for existing practitioners。With that out of the way， one more note before we jump into the good stuff: I find it slightly laughable that the authors believe that DevOps allows us to 'improve the human condition' - their ostensible reasoning being that better DevOps practices = less stressful work environment。 They seem to have missed the possibility that redeploying the 'human potential into something that's five times the value' could serve to exacerbate rather than reduce existing systemic and global issues。 I suppose that possibility is better ignored if you have built a career off of kowtowing to the corporate status quo （while DevOps can be said to innovate on processes， it does not in any way aim to challenge ultimate business outcomes）。 Lack of wokeness notwithstanding， let's jump in。 。。。more
John Davies
，
Most definitely learned a lot and thought of ways to improve the way we work。 Perhaps not as in-depth as some may like， but it gets the ideas out there and shines a light on what is possible。
Diogo Teixeira
，
Helpful， filled with great information。However， it is a concept book， so it is a bit "heavy" to read。 Helpful， filled with great information。However， it is a concept book， so it is a bit "heavy" to read。 。。。more
André
，
A good book on applying agile methods to the field of software engineering。The gist is that it's better to be good at recovering from mistakes than to be good at not making mistakes。This translates into:1。 Allow Devs to deploy to production within minutes2。 Decrease risk of failure by employing unit， integration， performance， and e2e testing3。 Allow Devs to know if their deployments succeeded or failed by providing telemetry4。 Create a culture where recovering from mistakes is more important tha A good book on applying agile methods to the field of software engineering。The gist is that it's better to be good at recovering from mistakes than to be good at not making mistakes。This translates into:1。 Allow Devs to deploy to production within minutes2。 Decrease risk of failure by employing unit， integration， performance， and e2e testing3。 Allow Devs to know if their deployments succeeded or failed by providing telemetry4。 Create a culture where recovering from mistakes is more important than not making them。My own contribution:1。 Tie deployment of features to real-life business goals， i。e。 before you actually start developing a feature， decide on the success and failure criteria for those features and build the necessary telemetry to make that decision。My only critique of the book is that it uses a little bit too much corporate speech where plain English would be clearer and I wish it went a little bit deeper with analyzing git flows and deployment pipelines。 。。。more
Vivek Sainanee
，
If you’ve worked as an engineer or PM in Silicon Valley for a few years or more， you really don’t need this book。The content isn’t wrong， but it seems like something you’d give to a 90s-era company to try making it modern。If you’re a new engineer， or perhaps an entrepreneur that wants to ensure you checked all the boxes， you might find some content useful， but that’s about it。
David
，
A really inspiring book， so much to think about。 I highly recommend to any and all IT professionals。 Now， true， I've yet to find a WAN provider who you might call Agile。 It's not all their fault， certainly I've seen jurisdictions make getting needed permits very slow and painful， yet there is still much to apply in any IT discipline。 A really inspiring book， so much to think about。 I highly recommend to any and all IT professionals。 Now， true， I've yet to find a WAN provider who you might call Agile。 It's not all their fault， certainly I've seen jurisdictions make getting needed permits very slow and painful， yet there is still much to apply in any IT discipline。 。。。more
Michael Burniston
，
Whereas The Phoenix Project answered the question "Why do we need modern DevOps practices？"， the DevOps Handbook describes exactly How to achieve this。 This book thankfully dispenses with the framework of delivering the information as a novel found within the former work。 Told in plain terms and backed up by real-world examples， this is the guidebook all organizations should follow if they intend to optimize how to deliver their product in a reliable， secure， agile manner。 Whereas The Phoenix Project answered the question "Why do we need modern DevOps practices？"， the DevOps Handbook describes exactly How to achieve this。 This book thankfully dispenses with the framework of delivering the information as a novel found within the former work。 Told in plain terms and backed up by real-world examples， this is the guidebook all organizations should follow if they intend to optimize how to deliver their product in a reliable， secure， agile manner。 。。。more
Rich
，
Good overview over nowadays indispensable software engineering practices without going too much into technical details and profound case studies。From my personal experience， DevOps practices of any kind （and even knowledge of their existence） are still missing in a majority of small software engineering teams （at least in Europe）。 It's not an exhaustive handbook of any kind。 It's rather a menu for an organization at their beginning of the good-practices journey to see what's in there and then pi Good overview over nowadays indispensable software engineering practices without going too much into technical details and profound case studies。From my personal experience， DevOps practices of any kind （and even knowledge of their existence） are still missing in a majority of small software engineering teams （at least in Europe）。 It's not an exhaustive handbook of any kind。 It's rather a menu for an organization at their beginning of the good-practices journey to see what's in there and then pick one and try to implement it。 。。。more
Manish Khare
，
A detailed book。 However the concepts are already well known。 What is being missed is the psychological approach。
Derek
，
I was familiar with most of the concepts due to following the DevOps boom via Reddit and HackerNews blogs。 I didn't feel like I gained too much but the book was good。 I was familiar with most of the concepts due to following the DevOps boom via Reddit and HackerNews blogs。 I didn't feel like I gained too much but the book was good。 。。。more
Tony
，
The Dev Ops Handbook does a great job of breaking down the how and why this process can be used in an organization to move forward in process change。 One of the quotes from the book that I love - "Innovation is impossible without risk taking， and if you haven't managed to upset a least some people in management， you're probably not trying hard enough。" The Dev Ops Handbook does a great job of breaking down the how and why this process can be used in an organization to move forward in process change。 One of the quotes from the book that I love - "Innovation is impossible without risk taking， and if you haven't managed to upset a least some people in management， you're probably not trying hard enough。" 。。。more
Jake Hayes
，
It's a good book for starting out in dev-ops or agile methodologies。 It's very focused on why and how to do it， so if you have experience setting it up or working with it already， someone else probably read this already and provided that information to you。 It's a good book for starting out in dev-ops or agile methodologies。 It's very focused on why and how to do it， so if you have experience setting it up or working with it already， someone else probably read this already and provided that information to you。 。。。more
Zumrud Huseynova
，
So-so。 I was expecting to get an understanding of overall DevOps， but what I did get is the philosophy of it， which is good to， but not meets my expectation from this book by it's name。 So-so。 I was expecting to get an understanding of overall DevOps， but what I did get is the philosophy of it， which is good to， but not meets my expectation from this book by it's name。 。。。more
Sooraj
，
6 months back I hardly knew much about DevOps or IT operations。 And now I know enough to have conversations and to ask questions。The book takes us through 3 DevOps principles: The principles of flow: from management of requirements and submission of code to the feature being productiveThe principles of feedback - how we get feedback through testing and monitoring as early as possible to ensure that we deliver value early fast and reliablyThe principles of continuous learning - institutionalizing 6 months back I hardly knew much about DevOps or IT operations。 And now I know enough to have conversations and to ask questions。The book takes us through 3 DevOps principles: The principles of flow: from management of requirements and submission of code to the feature being productiveThe principles of feedback - how we get feedback through testing and monitoring as early as possible to ensure that we deliver value early fast and reliablyThe principles of continuous learning - institutionalizing organizational learning and sharing， and codifying knowledge to make it a repetitive process。Reading characteristics:The content is rich。 Full of new ideas with good examples。 It's academic in nature， but more like a textbook， than a thesis。The ideas are philosophical as well as actionable - something you can start applying immediately。The language is simple for someone who is in IT。 But be a touch difficult for someone from non-IT background。 Because the topic itself is so technical， it's not a book which you can read super fast and continuously， unless you are a regular reader and knowledgeable and fluent with the terminology。 It's a book you need to read slowly， sometimes revisit already read parts to understand definitions and concepts and to cross-check。 I read it in parallel with another easier book to ensure that reading speed doesn't slow down altogether。The content more or less crisp。 Although some points are repeated， they are not out of context。 They are to either to remind the reader or to summarize chapters。Summary: If you are someone to me， been in IT， but new to DevOps， then this book is a real handbook。 It gives you a high to mid-level view of DevOps to not only get you started， but also leave you competent to have discussions and take first steps。 Worth every bit of penny and every second。 。。。more
Bartłomiej Falkowski
，
I first read The Phoenix Project by Gene Kim。 The Devops Handbook is a nice continuation of that book。 It describes the details and practices of The Three Ways - philosophy of DevOps。What I liked:- These two above books are consistent and complement each other - if you've read The Phoenix Project then The Devops Handbook is definitely worth reading。- The Three Ways principle adds nice separation of concerns - Flow， Feedback and Continual Learing and Experimentation- A lot of Case Studies and opi I first read The Phoenix Project by Gene Kim。 The Devops Handbook is a nice continuation of that book。 It describes the details and practices of The Three Ways - philosophy of DevOps。What I liked:- These two above books are consistent and complement each other - if you've read The Phoenix Project then The Devops Handbook is definitely worth reading。- The Three Ways principle adds nice separation of concerns - Flow， Feedback and Continual Learing and Experimentation- A lot of Case Studies and opinions from industry experts。 It gives some context and creates the atmosphere of realism and feasbility。- Practical advices 。 Obviously， because of the topic， vast majority of the book is a theory and an attempt to persuade the reader to change the way of thinking about Software Development Life Cycle。 However， I enjoyed the places where the authors gave some pragmatic tips， eg tool for integrating security into deployment pipeline。What I didn't like:- Those Case Studies are mostly from Google。。。 I don't deny the greatness of Google as a company but I immediately hear these arguments from coworkers - "We're not Google。。。"。- The last chapters about security - too long for the given value in my opinion。 。。。more
Chester Brian
，
A very well written book by some of the DevOps experts of our time。 It's highly informative and has tried to cover all the things you need to know about implementing DevOps in your organization。 If you're new to DevOps this book will definitely help you gain knowledge on how to get started。 Unfortunately， it's now showing its age especially when compared to some of the newer references out there。 A lot has been spent on trying to explain what CI or CD means， how automated testing works or how Se A very well written book by some of the DevOps experts of our time。 It's highly informative and has tried to cover all the things you need to know about implementing DevOps in your organization。 If you're new to DevOps this book will definitely help you gain knowledge on how to get started。 Unfortunately， it's now showing its age especially when compared to some of the newer references out there。 A lot has been spent on trying to explain what CI or CD means， how automated testing works or how Security can be injected into your pipeline。 These things are very common now， and people with more experience will find themselves constantly skimming these pages。 。。。more
Gaofeng
，
A guide for planning and executing DevOps transformations， a set of case studies to research and learn from， a chronicle of the history of DevOps， a means to create a coalition that spans Product Owners， Architecture， Development， QA， IT Operations， and Information Security to achieve common goals， a way to get the highest levels of leadership support for DevOps initiatives， as well as a moral imperative to change the way we manage technology organizations to enable better effectiveness and effi A guide for planning and executing DevOps transformations， a set of case studies to research and learn from， a chronicle of the history of DevOps， a means to create a coalition that spans Product Owners， Architecture， Development， QA， IT Operations， and Information Security to achieve common goals， a way to get the highest levels of leadership support for DevOps initiatives， as well as a moral imperative to change the way we manage technology organizations to enable better effectiveness and efficiency， as well as enabling a happier and more humane work environment， helping everyone become lifelong learner， this not only helps everyone achieve their highest goals as human beings， but also helps their organizations win。 。。。more
Kevin Boots
，
Great comprehensive overview of the concepts underpinning DevOps as discussed in the Phoenix Project。 This book elaborates on those concepts by offering a deepdive on how to implement these， what the technical implications of that are and how to kickstart your DevOps journey in general。 Recommended read for any engineer， manager or leader even remotely concerned with the software delivery journey。
Name
，
This is the worst book I've ever read。 This is the worst book I've ever read。 。。。more
Karthik Baalaa
，
Learn DevOps technology through books and institutes。 Here you see there is the best DevOps training institute in Chennai。 This is a fast-paced environment， and present applications must regularly be updated at an increasing momentum。 Besides， problems take place between developers and operational teams。 But the DevOps approach can solve this issue。 Well， what exactly is DevOps？ How will this culture enhance your career？ Why is it called culture or philosophy？ To know about this and more， enroll Learn DevOps technology through books and institutes。 Here you see there is the best DevOps training institute in Chennai。 This is a fast-paced environment， and present applications must regularly be updated at an increasing momentum。 Besides， problems take place between developers and operational teams。 But the DevOps approach can solve this issue。 Well， what exactly is DevOps？ How will this culture enhance your career？ Why is it called culture or philosophy？ To know about this and more， enroll in the best DevOps training institute in Chennai。 。。。more
Fereshteh Noori
，
If you are working in IT industry this is an absolute read book
Emran
，